-
Notifications
You must be signed in to change notification settings - Fork 191
Replace BinaryFormatter
with PSSerializer
#415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace BinaryFormatter
with PSSerializer
#415
Conversation
f967cb1
to
51abe90
Compare
Ah we need to figure out what depth is sufficient:
...I set it to 64. |
51abe90
to
167761d
Compare
@HowardWolosky the third commit is a little risker and you may want further testing of it. I verified my previous workflow still worked (and was previously erroring because of the use of |
d86320b
to
d152b79
Compare
d152b79
to
167761d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks so much for bringing this to my attention with the issue, as well as for providing the fix!
Your change looks good (aside from the minor requested capitalization change) from a code perspective. I just need to run it through some tests to verify that there aren't any unexpected regressions that I'm missing from a cursory review.
167761d
to
8f809fc
Compare
You're quite welcome! And yes, please verify it further. I use your module in a script to generate a changelog and programmatically create a GitHub release with assets uploaded direct from the CI/CD machines. It's great! I definitely want it to keep working with PowerShell 7.4. |
Since the former has been removed from PowerShell 7.4 (because it was removed from .NET 7) and the latter can accomplish the same thing. The default depth is 1, so we need to specify. Best I could find was that the prior implementation defaulted to a depth of 64, so we're going with that.
8f809fc
to
a59bbc2
Compare
Have you had a chance to test it more thoroughly yet? Thanks! |
Hey @HowardWolosky just following up on this as PowerShell 7.4 gets closer to GA (and will result in this module being quite broken without this change). 😄 |
PowerShell 7.4 has since hit GA, and this issue is starting to impact module consumers like myself. Is there anything we can do to help move this PR forward? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@andyleejordan - Thanks so much for getting this change in. My apologies for not completing the testing/validation earlier before PS 7.4 got released. Merging this in now, and then will see if I can get a new module version published.
Heck yeah, thanks @HowardWolosky! |
This has been published to PowerShellGallery as part of 0.17.0: https://www.powershellgallery.com/packages/PowerShellForGitHub/0.17.0 |
Description
Since the former has been removed from PowerShell 7.4 (because it was removed from .NET 7) and the latter can accomplish the same thing.
Issues Fixed
References
N/A
Checklist